System and method for in-SSD data processing engine selection based on stream IDs

ABSTRACT

A multi-stream memory system includes an in-device data processor including a first data processing engine and a second data processing engine, a controller processor, and a processor memory coupled to the controller processor, wherein the processor memory has stored thereon instructions that, when executed by the controller processor, cause the controller processor to perform: identifying a stream ID of an input stream, identifying the first data processing engine as being associated with the stream ID based on a stream assignment table, and applying the first data processing engine to the input stream to generate processed data.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority to, and the benefit of, U.S.Provisional Application No. 63/116,685 (“SYSTEM AND METHOD FOR IN SSDDATA PROCESSING ENGINE SELECTION BASED ON STREAM IDS”), filed on Nov.20, 2020, the entire content of which is incorporated herein byreference.

FIELD

Aspects of the present invention relate to the field of memory devices.

BACKGROUND

A solid-state drive/solid-state disk (SSD) is a solid-state storagedevice that uses integrated circuit (IC) assemblies as memory topersistently store data. SSD technology typically utilizes electronicinterfaces that are compatible with traditional block input/output (I/O)hard disk drives (HDDs), thereby providing easy replacement in manycommon applications.

A concept referred to as “multi-stream SSD” provides operating systemsand applications with interfaces that separately store data withdifferent attributes. These individual data stores are referred to as“streams.” Streams may be used to indicate when different data writesare associated with one another or have a similar lifetime. That is, agroup of individual data writes may be a part of a collective stream,and each stream is identified by a stream ID that is assigned by theoperating system or a corresponding application. Accordingly, differentdata having similar characteristics, or attributes, can each be assigneda unique stream ID such that data corresponding to that stream ID can bewritten to a same block in the SSD.

Currently, some SSDs allow for device-side processing, such ascompression or encryption of data within the SSD. Processing data in theSSD may provide numerous benefits, such as reducing host-side processingtime and CPU/memory consumption in a manner that may be transparent toapplications.

The SSDs of the related art treat all incoming data, such as data withdifferent stream IDs, in the same manner. For example, all incoming datamay be compressed and/or encrypted regardless of source or stream ID.However, typically, not all data needs to be compressed or encrypted.For instance, compressing already compressed data may result in largerthan original data size due to metadata overhead, and temporary dataresulting from data processing may not need to be encrypted.

Moreover, compression and encryption requirements may vary amongapplications. For examples, some applications may benefit from highcompression ratios while others may benefit from high compressionspeeds. However, these effects cannot generally be achieved at the sametime as, for example, high-compression algorithms have slow compressionspeeds. Furthermore, different applications may require differentencryption strengths, such as RSA or AES. Therefore, treating allincoming streams the same way at the SSD can introduce inefficienciesand undesirable results.

The above information disclosed in this Background section is only forenhancement of understanding of the invention, and therefore it maycontain information that does not form the prior art that is alreadyknown to a person of ordinary skill in the art.

SUMMARY

Aspects of embodiments of the present disclosure are directed towardmulti-streaming memory systems capable of in-SSD data processing engineselection based on stream IDs of incoming data. In some embodiments, themulti-streaming memory system improves performance and reduces powerconsumption by bypassing a compression engine when a data stream cannotbenefit from the compression and/or by bypassing an encryption enginewhen a data stream cannot benefit from the encryption.

According to an embodiment of the present invention, there is provided amulti-stream memory system including: an in-device data processorincluding a first data processing engine and a second data processingengine; a controller processor; and a processor memory coupled to thecontroller processor, wherein the processor memory has stored thereoninstructions that, when executed by the controller processor, cause thecontroller processor to perform: identifying a stream ID of an inputstream; identifying the first data processing engine as being associatedwith the stream ID based on a stream assignment table; and applying thefirst data processing engine to the input stream to generate processeddata.

In some embodiments, wherein the stream assignment table maps aplurality of stream IDs including the stream ID to a plurality of dataprocessing engines including the first and second data processingengines.

In some embodiments, the first data processing engine is configured toperform an operation different from the second data processing engine.

In some embodiments, the first data processing engine performs at leastone of compression, encryption, deduplication, search, and graphicsprocessing.

In some embodiments, the instructions further cause the processor toperform: identifying the second data processing engine as not beingassociated with the stream ID based on the stream assignment table; andin response to the identifying, bypassing the second data processingengine for the processed data.

In some embodiments, the instructions further cause the processor toperform: identifying the second data processing engine as beingassociated with the stream ID based on the stream assignment table; andin response to the identifying, applying the second data processingengine to the processed data.

In some embodiments, the in-device data processor is internal to andintegrated with a solid state drive (SSD) of the multi-stream memorysystem including the memory and the processor.

In some embodiments, the stream assignment table maps a plurality ofstream IDs including the stream ID to a plurality of physical addresseswithin one or more memory devices of the multi-stream memory system.

In some embodiments, the instructions further cause the processor toperform: identifying a physical address associated with the stream IDbased on the stream assignment table; and storing the processed data atthe physical address within a memory device of the multi-stream memorysystem.

In some embodiments, the instructions further cause the processor toperform: generating metadata associated with the processed data, themeta data indicating application of the first data processing engine tothe input stream; and storing the metadata along with the processed dataat the physical address within a memory device of the multi-streammemory system.

In some embodiments, applying the identified one of the first and seconddata processing engines includes: compressing the input stream by afirst compression engine to generate compressed data, and wherein theinstructions further cause the processor to perform: monitoring acompression ratio of the compressed data; determining that thecompression ratio is below a threshold; and In response to thedetermining, bypassing the identified one of the first and second dataprocessing engines for a remainder of input stream.

In some embodiments, the instructions further cause the processor toperform: providing the stream assignment table to a host, the host beinga source of the input stream.

According to an embodiment of the present invention, there is provided amulti-stream memory system including: an in-device data processorincluding a data processing engine; a controller processor; and aprocessor memory coupled to the controller processor, wherein theprocessor memory has stored thereon instructions that, when executed bythe controller processor, cause the controller processor to perform:identifying a first stream ID of a first input stream; identifying asecond stream ID of a second input stream; determining that the firststream ID is associated with the data processing engine based on astream assignment table; applying the data processing engine to thefirst input stream; and bypassing the data processing engine for thesecond input stream.

In some embodiments, the instructions further cause the processor toperform: determining that the second stream ID is not associated withthe data processing engine based on the stream assignment table.

In some embodiments, the stream assignment table maps a plurality ofstream IDs including the stream ID to a plurality of physical addresseswithin one or more memory devices of the multi-stream memory system.

In some embodiments, the instructions further cause the processor toperform: identifying a physical address associated with the secondstream ID based on the stream assignment table; and storing the secondinput stream at the physical address within a memory device of themulti-stream memory system.

According to an embodiment of the present invention, there is provided amethod of processing an input stream in a multi-stream memory system,the method including: identifying a stream ID of an input stream;identifying a first data processing engine of an in-device dataprocessor as being associated with the stream ID based on a streamassignment table, the in-device data processor including a second dataprocessing engine; and applying the first data processing engine to theinput stream to generate processed data.

In some embodiments, the stream assignment table maps a plurality ofstream IDs including the stream ID to a plurality of data processingengines including the first and second data processing engines.

In some embodiments, the method further includes: identifying the seconddata processing engine as not being associated with the stream ID basedon the stream assignment table; and in response to the identifying,bypassing the second data processing engine for the processed data.

In some embodiments, the method further includes: receiving the inputstream from a host, wherein the host associates the input stream withthe stream ID.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects of the present invention will be appreciated andunderstood with reference to the specification, claims, and appendeddrawings, wherein:

FIG. 1 is a block diagram illustrating a multi-stream memory system within-SSD data processing, according to some embodiments of the presentdisclosure.

FIG. 2 is a illustrates an example in which the multi-stream memorysystem bypasses the in-device data processing engines within the SSD fora particular stream, while performing in-device data processing forother streams, according to some embodiments of the present disclosure.

FIG. 3 is a block diagram illustrating a multi-stream memory systemutilizing middleware data processing, according to some embodiments ofthe present disclosure.

FIG. 4 is a flow diagram illustrating a method of processing an inputstream in a multi-stream memory system, according to some exampleembodiments of the present disclosure.

DETAILED DESCRIPTION

Features of the inventive concept and methods of accomplishing the samemay be understood more readily by reference to the following detaileddescription of embodiments and the accompanying drawings. Hereinafter,example embodiments will be described in more detail with reference tothe accompanying drawings, in which like reference numbers refer to likeelements throughout. The present invention, however, may be embodied invarious different forms, and should not be construed as being limited toonly the illustrated embodiments herein. Rather, these embodiments areprovided as examples so that this disclosure will be thorough andcomplete, and will fully convey the aspects and features of the presentinvention to those skilled in the art. Accordingly, processes, elements,and techniques that are not necessary to those having ordinary skill inthe art for a complete understanding of the aspects and features of thepresent invention may not be described. Unless otherwise noted, likereference numerals denote like elements throughout the attached drawingsand the written description, and thus, descriptions thereof will not berepeated. In the drawings, the relative sizes of elements, layers, andregions may be exaggerated for clarity.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which the present invention belongs. Itwill be further understood that terms, such as those defined in commonlyused dictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of the relevant art and/orthe present specification, and should not be interpreted in an idealizedor overly formal sense, unless expressly so defined herein.

In the storage stack of the related art, host data from differentapplications are mixed before sending to the solid-state drive (SSD).All data is compressed or encrypted inside SSD of the related art if theSSD compression or encryption engine is enabled. Thecompression/encryption engine may be turned off by an administrationcommand if it is known a dataset has a low compression ratio or does notneed to be encrypted. However, as there is only one data stream in SSDof the related art, turning off the compression/encryption engineaffects data from other applications as well, even when those otherapplications may have benefited from compression/encryption processingat the SSD.

Accordingly, aspects of the present disclosure provide a multi-streammemory system (e.g., a multi-stream flash drive) including a compressionengine and/or an encryption engine and capable of selectively bypassingthe compression engine and/or the encryption engine for data streamsthat cannot benefit from compression and/or encryption. In someembodiments, the multi-stream memory system is capable of selecting anappropriate data processing engine (e.g., a compression engine or anencryption engine) based on application requirements. In someembodiments, the multi-stream memory system selectively compressesand/or encrypts a stream based its stream ID, which may be assigned byeither a host or the multi-stream memory system. According to someembodiments, the controller of the multi-stream memory system canautomatically determine if a data stream should be compressed based onthe corresponding data stream's compression ratio and/or compressionspeed.

FIG. 1 is a block diagram illustrating a multi-stream memory system within-SSD data processing, according to some embodiments of the presentdisclosure. FIG. 2 is a illustrates an example in which the multi-streammemory system bypasses the in-device data processing engines within theSSD for a particular stream, while performing in-device data processingfor other streams, according to some embodiments of the presentdisclosure. FIG. 3 is a block diagram illustrating a multi-stream memorysystem utilizing mid-ware data processing, according to some embodimentsof the present disclosure.

Referring to FIG. 1, in some embodiments, the multi-stream memory system10 includes a multi-stream SSD (e.g., a multi-stream flash drive) 100with in-device data processing that is in data communication with a host20. The multi-stream SSD 100 includes an SSD controller 110, anin-device data processor 120, which is internal to and integrated withthe multi-stream SSD 100, and a non-volatile memory including aplurality of memory devices 130-1 to 130-M (where M is an integergreater than 1). In some examples, the memory devices 130 may be flashmemory devices (e.g., NAND flash memory devices).

The SSD controller 110 facilitates the transfer of data between the host20 and the SSD 100 through a plurality of streams 1 to N (where N is aninteger greater than 1). In some embodiments, the SSD controller 110includes a host interface layer 112 and a flash translation layer (FTL)114. The host interface layer 112 fetches application I/O requests fromthe host 20, translates the I/O requests into SSD internal read/writetransactions and schedules them to the FTL 114. The flash translationlayer (FTL) 114 acts as a translation layer between the sector-basedfile system of the host 20 and the memory devices 130 of the SSD 100.The host interface layer 112 and the FTL 114 may be implemented insoftware and/or hardware. The FTL 114 provides the operating system andthe file system on the host side access to the memory devices 130 andensures that they behave (or appear) as one block storage device. Insome examples, the FTL 114 hides the complexity of flash by providing alogical block interface to the flash memory device 130 by mapping thehost's logical addresses to the flash memory's physical addresses in alogical to physical (LtoP) table.

The data processor 120 acts as an embedded computer within the SSD 100and performs in-device data processing, such ascompression/decompression, encryption/decryption, searching operations,and/or graphics processing, for incoming and outgoing streams of data.The data processor 120 shifts processing close to where the data isstored and thus reduces the need to move data, which may be an expensiveoperation in terms of time and energy. For example, when running asearch, normally, large amounts of data on the storage device would haveto be moved over to the host, and searched on the host. However, withthe in-device data processor 120, one can send the inquiry to the SSD100 itself, and have the data processor 120 perform the search, andsimply return the result. As shown in FIG. 1, the data processor 120 mayinclude one or more compression engines 122, one or more encryptionengines 124, one or more deduplication engines 125, one or more searchengines 126, and/or one or more graphics processing engines 128.However, embodiments of the present invention are not limited thereto,and any suitable engine may be contained within the data processor 120.In some examples, the one or more compression engines 122 may perform atleast one of brotli, gzip, libdeflate, lzfse, and zstd compressions, andthe one or more encryption engines 124 may perform at least one ofchacha20-ietf, aes-256-gcm, aes-256-cfb, aes-256-ctr, andcamellia-256-cfb encryptions.

According to some embodiments, the SSD controller 110 selectivelyapplies data processing to streams based on their stream ID. In themulti-stream SSD, each input/output stream may be identified by a uniquestream ID, which may be encoded in the I/O command (e.g., by the host).The SSD controller 110 may enable or disable a particular dataprocessing engine for a given stream ID based on a stream assignmenttable, which maps each stream ID to one or more actions to be taken bythe SSD 100. The actions may, for example, include data placement,compression, encryption, search, and graphics processing. In someembodiments, the stream assignment table is coded in the firmware of theSSD 100, and is made available to the host 20. Therefore, eachapplication running at the host 20 may determine an appropriate streamID to use for its intended purpose.

Table 1 below illustrates an example of the stream assignment table in amulti-stream SSD 100 supporting 8 streams.

TABLE 1 Stream Number 1 2 3 4 5 6 7 8 Purpose Data Data Data Data DataData Data Data placement placement placement placement placementplacement placement placement Comp. Comp. Comp. Encrp. Encrp. SearchComp. Eng. 1 Eng. 2 Eng. 3 Eng. 1 Eng. 2 Eng. Eng. 1 Encrp. Eng. 2

As shown in table 1, each stream ID may be associated with a particularphysical address at the SSD 100. For example, each stream ID may beassociated with a different one of the flash memory devices 130.However, embodiments of the present disclosure are not limited thereto,and two or more stream IDs may be associated with a single physicaladdress or memory device 130 within the SSD 100. Additionally, eachstream ID may be associated with one or more data processing engines, ornot be associated with any data processing engine. For example, in Table1, stream IDs 1 to 3 are associated with compression engines 1 to 3,stream ID 7 is associated with both the compression engine 1 and theencryption engine 2, and stream ID 8 is not associated with anyin-device processing engine.

In some embodiments, when a stream of data arrives at the SSD 100, theSSD controller 110 (e.g. the host interface layer 112) checks the streamID of the incoming data, and based on the stream assignment table,determines what engines to direct the data to, and if no engine isspecified for the stream ID, to bypass the data processor 120 entirely(i.e., to not apply any of the engines in the data processor 120). Thebypassing of the compression and encryption engines for stream 8 in theexample of Table 1 is also visualized in FIG. 2.

In some embodiments, after applying the appropriate data processingengine, the SSD controller 110 tags each unit of processed data with theappropriate engine ID, and proceeds to store the data in thecorresponding location in the memory devices 130, which is based on thecorresponding data placement indicated in the stream assignment table.In some examples, once a unit of data is processed by a data processor120 (e.g., is compressed and/or encrypted), the FTL 114 records thecorresponding engine ID(s) in the meta data of the processed data, andstores it along with the processed data in the corresponding memorydevice(s). In some examples, a unit of data may be a logical page or agroup of pages that fit in a mapping entry size (e.g. 4 KB) in FTL.

When the host 20 sends a read request for the stored data, the SSDcontroller 110 (e.g., the FTL 114) determines what operation wasperformed on the stored data based on its meta data, and directs thedata processor 120 to perform the opposite operation. For example, whenthe data processor 120 compresses/encrypts a particular stream dataduring a write operation, the SSD controller 110 automatically instructsthe data processor 120 to decompress/decrypt the data when being readback by the host 20.

Knowledge of the stream assignment table allows applications of the host20 to select an appropriate in-SSD processing when it is beneficial tothe host 20 and/or SSD 100, and to bypass (e.g., not apply) in-SSD dataprocessing when such operations confer little to no benefit to the host20 or the SSD 100. As an example, in the case of Table 1 and FIG. 2,when data from Application C (shown in FIG. 2) has a low compressionratio, such that the SSD 100 cannot benefit from compressing data fromapplication C, the application may select to use stream ID 8, whichbypasses (e.g., does not apply) the compression engines of the dataprocessor 120, thus improving the performance (e.g., increase bandwidth)of the multi-stream SSD 100.

As illustrated in Table 1, in some examples, the data processor 120 mayinclude different types of compression engines (e.g., deflate(RFC-1951), ZLIB (RFC-1950), GZIP (RFC-1952), etc.) compression enginesand/or different types of encryption engines (e.g., RSA, AES, etc.), adata stream may be routed to compression/encryption engine that bestfits the data stream's compression/encryption requirement.

According to some embodiments, the SSD controller 110 is capable ofselecting an appropriate stream ID for a given stream. For example, theSSD controller 110 may monitor (e.g., in real time) the compressionratio of a stream undergoing compression, and when the stream'scompression ratio is less than a threshold, the SSD controller 110 mayredirect the stream to bypass the compression engine, by changing itsstream ID (to, e.g., a bypass stream ID). This stream ID change forbypassing purposes may be performed internally and temporarily, and maynot be communicated to the host 20. According to some examples, the SSDcontroller 110 may monitor the data being stored and bypassdeduplication if desired.

While FIG. 1 illustrates embodiments in which the data processor 120 isinternal to and integrated with the SSD 100, embodiments of the presentdisclosure are not limited thereto. For example, FIG. 3 illustratesembodiments in which the data processor 120-1 resides at a middlewaresystem 200 external to the SSD 100-1. The middleware system 200 mayreside in the cloud, or between a host operating system and theapplications running on it. In such examples, the data processor 120-1may be the same or substantially the same as the data processor 120 ofthe embodiments of FIG. 1, and the middleware system 200 may include anapplication interface layer 112-1 that processes I/O requests from thehost applications, similar to host interface layer 112 of theembodiments of FIG. 1. In some embodiments, the middleware controller210 processes the input streams (e.g., performs the stream ID detectionprocess) described above with respect to FIGS. 1 and 2 and is capable ofbypassing one or more data-processing engines as described above withrespect to FIGS. 1 and 2. The middleware system 200 maintains the streamID of the processed data so the host interface layer 112 of themulti-stream SSD 100-1 may identify/separate I/O streams based on streamID and allow streams to be stored at their corresponding locationswithin the memory devices 130.

perform stream ID-based placement on the processed data received fromthe middleware system 200, as described above.

FIG. 4 is a flow diagram illustrating a method 300 of processing aninput stream in a multi-stream memory system, according to some exampleembodiments of the present disclosure.

In some embodiments, upon receiving an input stream (e.g., from a hostthat associates the input stream with a stream ID), the SSD 100identifies the stream ID of the input stream (S302). The SSD 100 thenidentifies a first data processing engine among a plurality of dataprocessing engines of an in-device data processor 120 as beingassociated with the stream ID based on a stream assignment table (S304).The stream assignment table may map a plurality of stream IDs comprisingthe identified stream ID to the plurality of data processing engines.The SSD 100 then applies the first data processing engine to the inputstream to generate processed data, which may be stored within the SSD100 (S306). In some embodiments, the plurality of data processingengines includes a second data processing engine that is not associatedwith the stream ID. Here, the SSD 100 identifies the second dataprocessing engine as not being associated with the stream ID based onthe stream assignment table, and bypasses (e.g., does not apply) thesecond data processing engine for the processed data.

It will be understood that the above-described operations performed bythe multi-stream SSD 100 or the middleware system 200 and the SSD 100-1are merely example operations, and the operations performed by thesedevices may include various operations not explicitly described herein.

The operations performed by the constituent components of themulti-stream SSD (e.g., the SSD controller 110, the data processor 120,etc.) may be performed by a “processing circuit” or “processor” (e.g., acontroller processor) that may include any combination of hardware,firmware, and software, employed to process data or digital signals.Processing circuit hardware may include, for example, applicationspecific integrated circuits (ASICs), general purpose or special purposecentral processing units (CPUs), digital signal processors (DSPs),graphics processing units (GPUs), and programmable logic devices such asfield programmable gate arrays (FPGAs). In a processing circuit, as usedherein, each function is performed either by hardware configured (e.g.,hard-wired) to perform that function, or by more general-purposehardware, such as a CPU, configured to execute instructions stored in anon-transitory storage medium. A processing circuit may be fabricated ona single printed wiring board (PWB) or distributed over severalinterconnected PWBs. A processing circuit may contain other processingcircuits; for example, a processing circuit may include two processingcircuits, an FPGA and a CPU, interconnected on a PWB.

It will be understood that, although the terms “first”, “second”,“third”, etc., may be used herein to describe various elements,components, regions, layers, and/or sections, these elements,components, regions, layers, and/or sections should not be limited bythese terms. These terms are used to distinguish one element, component,region, layer, or section from another element, component, region,layer, or section. Thus, a first element, component, region, layer, orsection discussed below could be termed a second element, component,region, layer, or section, without departing from the scope of theinventive concept.

The terminology used herein is for the purpose of describing particularembodiments and is not intended to be limiting of the inventive concept.As used herein, the singular forms “a” and “an” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “include”,“including”, “comprises”, and/or “comprising”, when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof. As used herein,the term “and/or” includes any and all combinations of one or more ofthe associated listed items. Further, the use of “may” when describingembodiments of the inventive concept refers to “one or more embodimentsof the inventive concept”. Also, the term “exemplary” is intended torefer to an example or illustration.

It will be understood that when an element, layer, region, or componentis referred to as being “on,” “connected to,” or “coupled to” anotherelement, layer, region, or component, it can be directly on, connectedto, or coupled to the other element, layer, region, or component, or oneor more intervening elements, layers, regions, or components may bepresent. In addition, it will also be understood that when an element orlayer is referred to as being “between” two elements or layers, it canbe the only element or layer between the two elements or layers, or oneor more intervening elements or layers may also be present.

As used herein, the terms “use”, “using”, and “used” may be consideredsynonymous with the terms “utilize”, “utilizing”, and “utilized”,respectively.

For the purposes of this disclosure, “at least one of X, Y, and Z” and“at least one selected from the group consisting of X, Y, and Z” may beconstrued as X only, Y only, Z only, or any combination of two or moreof X, Y, and Z, such as, for instance, XYZ, XYY, YZ, and ZZ.

Further, the use of “may” when describing embodiments of the inventiveconcept refers to “one or more embodiments of the inventive concept.”Also, the term “exemplary” is intended to refer to an example orillustration.

When a certain embodiment may be implemented differently, a specificprocess order may be performed differently from the described order. Forexample, two consecutively described processes may be performedsubstantially at the same time or performed in an order opposite to thedescribed order.

While this invention has been described in detail with particularreferences to illustrative embodiments thereof, the embodimentsdescribed herein are not intended to be exhaustive or to limit the scopeof the invention to the exact forms disclosed. Persons skilled in theart and technology to which this invention pertains will appreciate thatalterations and changes in the described structures and methods ofassembly and operation can be practiced without meaningfully departingfrom the principles, spirit, and scope of this invention, as set forthin the following claims and equivalents thereof.

What is claimed is:
 1. A multi-stream memory system comprising: anin-device data processor comprising a first data processing engine and asecond data processing engine; a controller processor; and a processormemory coupled to the controller processor, wherein the processor memoryhas stored thereon instructions that, when executed by the controllerprocessor, cause the controller processor to perform: identifying astream ID of an input stream; identifying the first data processingengine as being associated with the stream ID based on a streamassignment table stored at the multi-stream memory system, the streamassignment table mapping the stream ID to the first data processingengine, the first data processing engine comprising at least one of adeduplication engine, a data search engine, and a graphics engine; andapplying the first data processing engine to the input stream togenerate processed data.
 2. The multi-stream memory system of claim 1,wherein the stream assignment table comprises a mapping of the stream IDto the first data processing engine and maps another stream ID to thesecond data processing engine.
 3. The multi-stream memory system ofclaim 1, wherein the first data processing engine is configured toperform an operation different from the second data processing engine.4. The multi-stream memory system of claim 1, wherein the first dataprocessing engine performs at least one of deduplication, search, andgraphics processing.
 5. The multi-stream memory system of claim 1,wherein the instructions further cause the controller processor toperform: bypassing the second data processing engine for the processeddata.
 6. The multi-stream memory system of claim 1, wherein theinstructions further cause the controller processor to perform:identifying the second data processing engine as being associated withthe stream ID based on the stream assignment table; and in response tothe identifying, applying the second data processing engine to theprocessed data.
 7. The multi-stream memory system of claim 1, whereinthe in-device data processor is internal to and integrated with a solidstate drive (SSD) of the multi-stream memory system comprising theprocessor memory and the controller processor.
 8. The multi-streammemory system of claim 1, wherein the stream assignment table maps thestream ID to a physical address within a memory device of themulti-stream memory system.
 9. The multi-stream memory system of claim1, wherein the instructions further cause the controller processor toperform: identifying a physical address associated with the stream IDbased on the stream assignment table; and storing the processed data atthe physical address within a memory device of the multi-stream memorysystem.
 10. The multi-stream memory system of claim 9, wherein theinstructions further cause the controller processor to perform:generating metadata associated with the processed data, the metadataindicating application of the first data processing engine to the inputstream; and storing the metadata along with the processed data at thephysical address within a memory device of the multi-stream memorysystem.
 11. The multi-stream memory system of claim 1, wherein applyingthe identified one of the first and second data processing enginescomprises: compressing the input stream by a first compression engine togenerate compressed data, and wherein the instructions further cause thecontroller processor to perform: monitoring a compression ratio of thecompressed data; determining that the compression ratio is below athreshold; and In response to the determining, bypassing the identifiedone of the first and second data processing engines for a remainder ofthe input stream.
 12. The multi-stream memory system of claim 1, whereinthe instructions further cause the controller processor to perform:providing the stream assignment table to an external device, theexternal device being a source of the input stream.
 13. A multi-streammemory system comprising: an in-device data processor comprising a dataprocessing engine; a controller processor; and a processor memorycoupled to the controller processor, wherein the processor memory hasstored thereon instructions that, when executed by the controllerprocessor, cause the controller processor to perform: identifying afirst stream ID of a first input stream; identifying a second stream IDof a second input stream; determining that the first stream ID isassociated with the data processing engine based on a stream assignmenttable stored at the multi-stream memory system, the stream assignmenttable mapping the first stream ID to the data processing engine, thedata processing engine comprising at least one of a deduplicationengine, a data search engine, and a graphics engine; applying the dataprocessing engine to the first input stream; and bypassing the dataprocessing engine for the second input stream.
 14. The multi-streammemory system of claim 13, wherein the stream assignment table maps thefirst stream ID to a physical address within a memory device of themulti-stream memory system.
 15. The multi-stream memory system of claim13, wherein the instructions further cause the controller processor toperform: identifying a physical address associated with the secondstream ID based on the stream assignment table; and storing the secondinput stream at the physical address within a memory device of themulti-stream memory system.
 16. A method of processing an input streamin a multi-stream memory system, the method comprising: identifying, bya controller processor, a stream ID of the input stream; identifying, bythe controller processor, a first data processing engine of an in-devicedata processor as being associated with the stream ID based on a streamassignment table stored at the multi-stream memory system, the streamassignment table mapping the stream ID to the first data processingengine, the first data processing engine comprising at least one of adeduplication engine, a data search engine, and a graphics engine; andapplying, by the controller processor, the first data processing engineto the input stream to generate processed data.
 17. The method of claim16, wherein the stream assignment table comprises a mapping of thestream ID to the first data processing engine.
 18. The method of claim16, further comprising: bypassing, by the controller processor, a seconddata processing engine of the in-device data processor for the processeddata.
 19. The method of claim 16, further comprising: receiving theinput stream from an external device, wherein the external deviceassociates the input stream with the stream ID.